Limitations
Last updated: 2026-11-16How the endpoint identifies changes
HANA assigns an internal row ID to each physical row version. On each capture cycle, the SAP add-on compares snapshots of table keys and row IDs. An unchanged row ID indicates no change; a higher row ID indicates an update; a key missing from the new snapshot indicates a delete; and a new key indicates an insert. The add-on reads the full row for inserts and updates, then writes the change to the table changelog.
Multiple operations on the same primary key during one polling interval can collapse into a single net change:
| Operations | Change sent to Qlik Replicate |
|---|---|
| Insert, then update | Insert |
| Insert, then delete | No change |
| Multiple updates | Update with the last image |
| Update, then delete | Delete |
| Delete, then insert with the same key | Update |
Set the task's Apply Conflicts behavior to upsert on insert and no-op on a missing update or delete. At-least-once delivery, full-load and CDC overlap, and delete-then-insert handling can otherwise create target conflicts.
Current limitations
- The endpoint captures table data by snapshot comparison only. It does not use triggers, database logs, ODP, CDS views, or extractors.
- Row-store tables and SAP S/4HANA Public Cloud systems are not supported.
- An SAP admin must register and enable each table before it appears in Qlik Replicate.
- If a primary key's row ID moves backwards, often after a table is repartitioned, restructured, or truncated, the endpoint suspends the table and requires a reload.
- HANA multi-node redistribution can reassign row IDs across a table and appear as updates, even when the row values did not change.
- The endpoint records change-detection time, not the original transaction time or the user who made the change.
- A source table DDL change requires a full rebaseline.
- A task can capture at most 1,000 tables from this endpoint. This limit cannot be changed. Split larger workloads across tasks.
- Table filters are applied by Qlik Replicate after SAP sends the records; filters are not sent to SAP.
- Full LOB mode is not supported. For supported type mappings and LOB behavior, see Supported data types.